The com.voicegenie.logtoasr Property

The IP Media Server can write call information (call start/call end, and <log> content) directly to the OSR SWIevent log. That means that if you are running OSDMs (or any application that uses the OSDM logging format), the resulting SWIevent log can be loaded into OpenSpeech Insight (OSI) for analysis, without requiring any pre-processing.

For example, if your application executes <log>test</log>, then something like the following might be written to the SWIevent log:

TIME=20050207134707093|...|EVNT=SWIurlg|test|UCPU=0|SCPU=0

Configuration

To use this feature, the following configuration is required. (This should all be set correctly by default, but if data is not being written to the SWIevent log as expected, something may have been manually changed since installation.)

1. The defaults file should contain <property name="com.voicegenie.logtoasr" value="true"/> (neither the name nor the value is case-sensitive).



2. In the SIP stack Configuration, asr.log_metrics_to_asr should be set to 1.



3. In the ASR Manager Configuration, ASR_MANAGER.ENGINE_TO_LOG_METRICS should be set to SPEECHWORKS.



4. Also in the ASR Manager Configuration, ASR_MANAGER.ALLOCATE_WITH_LOGGING should be set to FALSE for all-in-one installations, or TRUE for client/server installations.

Note: The IP Media Server will stop writing logs to the SWIevent log once the caller hangs up, even though it might still be writing <log>s to the pw_metricsfile (while doing cleanup in a hangup event handler). This means that if you are using the OSDM logging format, some end events (ex. SWIdmnd, SWIphnd, SWIstnd, etc.) might not be written to the SWIevent log. In that case, the SWIevent log can still be loaded into OSI, and most accuracy numbers and timing information related to recognition should be unaffected. However, some other statistics, such as those related to the DialogModule, may be inaccurate.